Description

Increase the wait time for FirebaseRemoteConfigTest.TestAddOnConfigUpdateListener from 10s to 30s to reduce test flakiness.

As shown on #1179, the realtime integration test is flaky.

I looked into the logs and all of the failures fail at the point of waiting 10s for the promise to indicate that an updated config has been fetched (example). I looked into a number of other logs and see that even though most runs of this test finish in less than 3 seconds, around 10% of the successes take 5-10 seconds, so the flaky failures are likely just taking slightly longer than normal due to slow network or other delays. 30 seconds should be enough to significantly reduce the flakiness.

Testing

N/A. The change is trivial. Investigated our archive of github test logs to see how often the test takes 10s or almost 10s.

Type of Change

Place an x the applicable box:

• Bug fix. Add the issue # below if applicable.
• New feature. A non-breaking change which adds functionality.
• Other, such as a build process or documentation change.

Notes

• Bug fixes and feature changes require an update to the Release Notes section of release_build_files/readme.md.
• Read the contribution guidelines CONTRIBUTING.md.
• Changes to the public API require an internal API review. If you'd like to help us make Firebase APIs better, please propose your change in a feature request so that we can discuss it together.